Important: OpenShift Container Platform 4.10.30 bug fix and security update

Synopsis

Important: OpenShift Container Platform 4.10.30 bug fix and security update

Type/Severity

Security Advisory: Important

Topic

Red Hat OpenShift Container Platform release 4.10.30 is now available with
updates to packages and images that fix several bugs and add enhancements.

This release includes a security update for Red Hat OpenShift Container Platform 4.10.

Red Hat Product Security has rated this update as having a security impact
of Important. A Common Vulnerability Scoring System (CVSS) base score,
which gives a detailed severity rating, is available for each vulnerability
from the CVE link(s) in the References section.

Description

Red Hat OpenShift Container Platform is Red Hat's cloud computing
Kubernetes application platform solution designed for on-premise or private
cloud deployments.

This advisory contains the container images for Red Hat OpenShift Container Platform 4.10.30. See the following advisory for the RPM packages for this release:

https://access.redhat.com/errata/RHBA-2022:6132

Space precludes documenting all of the container images in this advisory. See the following Release Notes documentation, which will be updated shortly for this release, for details about these changes:

https://docs.openshift.com/container-platform/4.11/release_notes/ocp-4-11-release-notes.html

Security Fix(es):

  • go-getter: command injection vulnerability (CVE-2022-26945)
  • go-getter: unsafe download (issue 1 of 3) (CVE-2022-30321)
  • go-getter: unsafe download (issue 2 of 3) (CVE-2022-30322)
  • go-getter: unsafe download (issue 3 of 3) (CVE-2022-30323)

For more details about the security issue(s), including the impact, a CVSS
score, acknowledgments, and other related information, refer to the CVE
page(s)
listed in the References section.

You may download the oc tool and use it to inspect release image metadata as follows:

(For x86_64 architecture)

$ oc adm release info quay.io/openshift-release-dev/ocp-release:4.10.30-x86_64

The image digest is sha256:7f543788330d486627c612c64eebc8e992944991e21cfdb771fd36725b277f07

(For s390x architecture)

$ oc adm release info quay.io/openshift-release-dev/ocp-release:4.10.30-s390x

The image digest is sha256:f18a9ef98677dbfeace3d39ee2bdbe4e1d59004b4df64ebc031214d4107c2e6b

(For ppc64le architecture)

$ oc adm release info quay.io/openshift-release-dev/ocp-release:4.10.30-ppc64le

The image digest is sha256:ad1e037867f067d040a35ec33d3b39bc19410da9fe91006b6217e122152a250e

(For aarch64 architecture)

$ oc adm release info quay.io/openshift-release-dev/ocp-release:4.10.30-aarch64

The image digest is sha256:f1b28e9c2a3e29565140b56bee2172dd5e83f3edbe683c240301155a01842f53

All OpenShift Container Platform 4.10 users are advised to upgrade to these updated packages and images when they are available in the appropriate release channel. To check for available updates, use the OpenShift Console or the CLI oc command. Instructions for upgrading a cluster are available
at https://docs.openshift.com/container-platform/4.10/updating/updating-cluster-cli.html

Solution

For OpenShift Container Platform 4.10 see the following documentation,
which will be updated shortly for this release, for important instructions
on how to upgrade your cluster and fully apply this asynchronous errata
update:

https://docs.openshift.com/container-platform/4.10/release_notes/ocp-4-10-release-notes.html

Details on how to access this content are available at
https://docs.openshift.com/container-platform/4.10/updating/updating-cluster-cli.html

Affected Products

  • Red Hat OpenShift Container Platform 4.10 for RHEL 8 x86_64
  • Red Hat OpenShift Container Platform for Power 4.10 for RHEL 8 ppc64le
  • Red Hat OpenShift Container Platform for IBM Z and LinuxONE 4.10 for RHEL 8 s390x
  • Red Hat OpenShift Container Platform for ARM 64 4.10 aarch64

Fixes

  • BZ - 2051267 - When 'oc adm upgrade --to-image ...' rejects an update as not recommended, it should mention --allow-explicit-upgrade
  • BZ - 2070392 - [OVN AWS] EgressIP was not balanced to another egress node after original node was removed egress label
  • BZ - 2092918 - CVE-2022-30321 go-getter: unsafe download (issue 1 of 3)
  • BZ - 2092923 - CVE-2022-30322 go-getter: unsafe download (issue 2 of 3)
  • BZ - 2092925 - CVE-2022-30323 go-getter: unsafe download (issue 3 of 3)
  • BZ - 2092928 - CVE-2022-26945 go-getter: command injection vulnerability
  • BZ - 2095111 - [ovn] northd container termination script must use bash
  • BZ - 2099584 - [Bare Metal IPI] BMH pre-provisoning netowrk configurations are not preserved when machineset replicas are scaled up/down
  • BZ - 2114587 - All critical alerts should have links to a runbook
  • BZ - 2115874 - Default catalogs fails liveness/readiness probes
  • BZ - 2116624 - etcd-metrics container is flooding logs
  • BZ - 2116642 - bond-cni: Backport "mac duplicates" 4.11
  • BZ - 2116983 - flaky e2e in kube-controller-manager-operator TestPodDisruptionBudgetAtLimitAlert
  • BZ - 2117351 - README file for helm charts coded in Chinese shows messy characters when viewing in developer perspective.
  • BZ - 2118607 - [OVN] bonding fails after active-backup fail-over and reboot, kargs static IP
  • BZ - 2118609 - OVS-Configure doesn't iterate connection names containing spaces correctly
  • OCPBUGS-235 - ClusterVersion availableUpdates is stale: PromQL conditional risks vs. slow/stuck Thanos
  • OCPBUGS-200 - Exits with a non-zero code in case Etcd backup fails
  • OCPBUGS-376 - storageclass should not be created for unsupported vsphere version
  • OCPBUGS-287 - [OVN] bonding fails after active-backup fail-over and reboot, kargs static IP
  • OCPBUGS-249 - Incorrect NAT when using cluster networking in control-plane nodes to install a VRRP Cluster
  • OCPBUGS-205 - [release-4.10] Add support for BUILDAH_QUIET environment variable
  • OCPBUGS-419 - OVS-Configure doesn't iterate connection names containing spaces correctly
  • OCPBUGS-233 - Upgrade failing because restrictive scc is injected into version pod
  • OCPBUGS-174 - [OVN] New pods unable to establish TCP connections and get constant timeouts causing application downtime